โ RNS 1.4.2 released https://pypi.org/project/rns/
๐ฌค rns.recipes
top
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ RFed Release Candidate โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Started by jrl290 ยท 2mo ago
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-1
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ jrl290 #1 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 2mo ago
https://github.com/jrl290/RFed
I feel that I've done all that I can on my own to test what I hope will be a boon for
Reticulum. I want to freeze the protocol. But I want to expose it to the harshness of the
internet first
Here's the premise:
โข RFed is an extension on the principles of LXMF store-and-forward propagation - a
layer of nodes between backbone servers and endpoint devices collects and synchronizes
data published to it
โข Endpoint devices then connect to a middle node to pull messages on the network
designated for that device
โข RFed adds to this mechanism the ability to subscribe to a data channel in a global
namespace. The RFed node then considers messages published to a channel to be designated
for any device that has subscribed to that channel
โข In addition, RFed adds the ability to register a destination to be pinged when data
designated for a device is available
โข Lastly, RFed has a built in LXMF store-and-forward service, completely compliant to
spec. It is designed to replace the standalone LXMF propagation service
Why it adds foundational capability to Reticulum:
โข It adds subscriber based communication to the Reticulum network itself. Instead of a
single host being a single point of control and failure for message distribution
applications, a mass of nodes stores and forwards data without any knowledge of what the
packet contains
โข It expands the hard point representation for devices that are not always online.
Sending notification pings to relays enables true mobile push notifications
Privacy and data security is still paramount:
โข Packets are double wrapped the same way that LXMF propagation packets are.
Intermediary nodes cannot see any data in any packet without the private key for the
channel, which is shared out of band. All intermediary nodes are considered untrusted.
โข Even when a channel is considered "public", the destination address is hashed before
an RFed node sees it, obfuscating the "public" part of the address
โข Stamp costs are configurable for both internode peering and publishing to channels
Considerations:
โข It is currently still possible to spam messages over channels if their RFed node is
given a stamp cost of 0. I'm not entirely sure how to protect against that, but channels
are not just for chats so I didn't want to do any sort of naive filtering just. Maybe
someone has ideas
โข It is possible to send large data packages over RFed. But each node does have
configurable storage limits as well as transfer and sync size limits
โข When it comes to distribution to subscribers, each endpoint device has one RFed node
that services it (although there isn't really a reason it couldn't have more than one I
don't think). However, RFed has built in the ability to assign a backup node in case it
goes offline. These nodes are supposed to be a highly available point that fills in for
the highly unavailable endpoint devices. So redundancy I felt was important to build in
Of course, currently the only up and running RFed node is mine. And the only app that
makes use of it is my Retichat for iPhone and Android. But whoever is interested in
tinkering with, vetting, penetration testing, or building on top of, I would very much
appreciate the feedback
Hopefully there aren't any more changes to be made and others can take advantage of the
new capability
โ 2 โ 0 โค 4
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-2
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ nim #2 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 1mo ago
Has your node gone down? I cant seem to reach it.
โ 0 โ 0 โค 0
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-3
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ jrl290 #3 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 1mo ago
nim wrote:
> Has your node gone down? I cant seem to reach it.
I am able to propagate send and channel send through it (through the backbone network).
I'm not able to channel subscribe, it seems. So I'll have to check that out
โ 0 โ 0 โค 0
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-4
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ Dio #4 โ
โ 640663f2d810e446 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 1mo ago
I can't join a channel from Retichat iOS
โ 0 โ 0 โค 0
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-5
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ jrl290 #5 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 1mo ago
Dio wrote:
> I can't join a channel from Retichat iOS
A thread deadlock caused the freeze of the channels mechanism in RFed. When I rebooted
the node it came back. I made some changes to that mechanism to hopefully prevent it from
happening again and it's be running fine for a couple days now. But threading issues are
tough to track and diagnose, just fyi
โ 1 โ 0 โค 1
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-6
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ batrat #6 โ
โ 500e6ab103644d28 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 1mo ago
I still can't send/receive messages. All other Reticulum apps work on my phone though.
Could other Reticulum apps be conflicting with Retichat? I also don't have Play Services
installed but I doubt connectivity (or anything) relies on them?
โ 0 โ 0 โค 0
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
post-7
โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ
โ batrat #7 โ
โ 500e6ab103644d28 โ
โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ
โธ 1mo ago
I'm sorry, I double posted this by accident on two different threads.
โ 0 โ 0 โค 0
โ INFO โ Identify to this node to post. How?
bottom